…+ tests

…ion to avoid problems on other searches made on same method

…mputed

… README

Currently translated at 100.0% (8 of 8 strings)

Translation: purchase-workflow-13.0/purchase-workflow-13.0-procurement_purchase_no_grouping
Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-13-0/purchase-workflow-13-0-procurement_purchase_no_grouping/zh_CN/

When purchase grouping is set to no order grouping, the previously returned domain
ensured no other PO is found, but being the same domain for all will make that they
are grouped together in a batch operation, like the creation of all procurements
from a confirmed sales order.

Steps to reproduce:

* Create 2 products with MTO and different vendors.
* Add both in a sales order.
* Confirm the sales order.
* One purchase order is created for both products instead of 2, more even in this
  case that they have different vendors.

Fixes OCA#975

…red_purchase_grouping field

Steps to reproduce:

- Create a product with MTO route and "No line grouping" product
  category.
- Create an SO with such product and quantity = 1.
- Confirm it.
- A purchase order is created with such product and qty = 1.
- Edit the sales order, and change quantity = 2.

Current behavior:

A new purchase line is created with quantity = 2, having ordered 3 units
instead of 2.

Expected behavior:

The same existing purchase line is updated with quantity = 2.

------

For solving this problem, we are going to group by procurement group
instead of simply discarding any possible line grouping.

NOTE: This makes that if you manually assign the same procurement group
to several different sales orders, the grouping will be done no matter
the grouping criteria, but this is the only way to do it without having
to put a lot of glue modules, and on standard operation mode,
procurement groups are not reused between sales orders.

TT33031